Fetch a :ref:`ref_flyteidl.admin.LaunchPlan` definition
Retrieve an existing launch plan definition.
Path Parameters
Name of the project the resource belongs to.
Name of the domain the resource belongs to. A domain can be considered as a subset within a specific project.
User provided value for the resource.
Specific version of the resource.
Query Parameters
Identifies the specific type of resource that this identifier corresponds to.
- DATASET: A dataset represents an entity modeled in Flyte DataCatalog. A Dataset is also a versioned entity and can be a compilation of multiple individual objects. Eventually all Catalog objects should be modeled similar to Flyte Objects. The Dataset entities makes it possible for the UI and CLI to act on the objects in a similar manner to other Flyte objects
UNSPECIFIED, TASK, WORKFLOW, LAUNCH_PLAN, DATASET Optional, org key applied to the resource.
Response
A successful response.
A LaunchPlan provides the capability to templatize workflow executions. Launch plans simplify associating one or more schedules, inputs and notifications with your workflows. Launch plans can be shared and used to trigger executions with predefined inputs even when a workflow definition doesn't necessarily have a default value for said input.
Encapsulation of fields that uniquely identifies a Flyte resource.
User-provided launch plan definition and configuration values.
Values computed by the flyte platform after launch plan registration. These include expected_inputs required to be present in a CreateExecutionRequest to launch the reference workflow as well timestamp values associated with the launch plan.